Detailed Breakdown

The file contains three distinct functional domains:

1. Main Configuration Generation (lines 58-445)

• generateSafeOutputsConfig() - 387 lines
• Massive function with 84 conditional branches checking SafeOutputs fields
• Repetitive pattern: check if field exists → call helper → add to config map
• Clear candidates for extraction: each safe-output type could be a separate handler

2. Tool Definition Generation (lines 449-535)

• generateCustomJobToolDefinition() - 87 lines
• Converts SafeJobConfig into MCP tool definitions
• Self-contained logic for custom job schema generation
• Input type mapping (choice → string with enum, boolean, number, string)

3. Filtered Tools and Repo Parameter Handling (lines 539-926)

• generateFilteredToolsJSON() - 242 lines
  • Loads all tools, filters based on enabled SafeOutputs
  • Adds custom job tools (sorted for deterministic output)
  • Generates dispatch_workflow tools dynamically
  • Heavy function with multiple responsibilities
• addRepoParameterIfNeeded() - 147 lines
  • Massive switch statement handling repo parameter injection
  • Repetitive pattern for each tool type
  • Could benefit from data-driven approach

4. Dispatch Workflow Tool Generation (lines 930-1023)

• generateDispatchWorkflowTool() - 94 lines
• Converts GitHub Actions workflow_dispatch inputs to MCP tool schema
• Input type mapping similar to custom job tools

Helper Functions Already Extracted:

• safe_outputs_config_generation_helpers.go - Contains generateMaxConfig, generatePullRequestConfig, etc.
• tool_description_enhancer.go - Contains enhanceToolDescription

Complexity Hotspots

1. generateSafeOutputsConfig() (lines 58-445):

   • 84 conditional branches checking different SafeOutputs fields
   • Highly repetitive pattern that could be data-driven
   • Lines 69-340: Create/update/close operations
   • Lines 342-379: Custom jobs handling
   • Lines 381-441: Mentions and dispatch-workflow configuration

2. generateFilteredToolsJSON() (lines 539-777):

   • Multiple responsibilities: filtering, enhancing, custom jobs, dispatch workflows
   • Lines 560-656: Building enabledTools map (97 lines of repetitive checks)
   • Lines 685-707: Custom job tools generation
   • Lines 713-765: Dispatch workflow tools generation

3. addRepoParameterIfNeeded() (lines 781-926):

   • Massive switch statement with repetitive patterns
   • Each case checks config for hasAllowedRepos and targetRepoSlug
   • Lines 845-895: Nested switch for SafeOutputTargetConfig tools

Duplicate/Similar Patterns

1. Config generation pattern (repeated 30+ times):

   if data.SafeOutputs.FieldName != nil {
       safeOutputsConfig["tool_name"] = generateHelper(...)
   }

2. Tool enablement pattern (repeated 30+ times):

   if data.SafeOutputs.FieldName != nil {
       enabledTools["tool_name"] = true
   }

3. Repo parameter check pattern (repeated 15+ times):

   if config := safeOutputs.FieldName; config != nil {
       hasAllowedRepos = len(config.AllowedRepos) > 0
       targetRepoSlug = config.TargetRepoSlug
   }